Though we did produce what we ourselves consider a good and extensive requirements document there are a few areas in our work process that could have been done better.

\subsection{Scope}
We started this project with a very realistic look on it rather than looking at it as just an academic project. This meant that we had a too large scope for our project and we produced a lot of requirements, maybe not as much as a real mobile phone application would have, but still more than the usual academic project.
Because of this we felt a lot of stress during the project which led to many parts being a bit rushed.
We should have followed either of two options. Either focus on a simpler application with just a map view feature and the requirements that would be necessary for this; or we should not have gone into so much detail for the application we chose to work with and keep a higher domain in order to not be overwhelmed by the amount of requirements elictated or by the work it took to specify them all at the level we chose.

\subsection{Documentation}
Another problem our group encounterd was that we did not quite understand how important it was to document the elicitation or specification processes as they were being carried out. At least no detailed documentation were done but only short notes by various members of the team.
Because of this we encountered some problems when writing down exactly what we had done as much would have to be taken from memory or decoded from very incomplete and short notes.
